Skip to content

refactor(@angular-devkit/core): use package exports field for secondary entries#25258

Merged
clydin merged 1 commit intoangular:mainfrom
clydin:build/core-remove-legacy-secondary
May 23, 2023
Merged

refactor(@angular-devkit/core): use package exports field for secondary entries#25258
clydin merged 1 commit intoangular:mainfrom
clydin:build/core-remove-legacy-secondary

Conversation

@clydin
Copy link
Copy Markdown
Member

@clydin clydin commented May 22, 2023

The secondary entry point (node) within the @angular-devkit/core package is now defined by an exports entry in the main package.json file for the package. This removes the need for the additional nested package.json file in a subdirectory. The exports field also contains backward compatible entries to allow for continued deep imports into the package. These compatibility entries will, however, be removed in a future major version. Deep imported files are not considered part of the public API of the package.

@clydin clydin added the target: minor This PR is targeted for the next minor release label May 22, 2023
@clydin clydin force-pushed the build/core-remove-legacy-secondary branch 7 times, most recently from 59ef1be to 9fa10ad Compare May 22, 2023 18:10
@clydin clydin requested a review from alan-agius4 May 22, 2023 18:29
@clydin clydin added the action: review The PR is still awaiting reviews from at least one requested reviewer label May 22, 2023
Comment thread packages/angular_devkit/core/package.json
Comment thread packages/angular_devkit/core/package.json Outdated
…ry entries

The secondary entry point (`node`) within the `@angular-devkit/core` package is
now defined by an exports entry in the main package.json file for the package. This
removes the need for the additional nested package.json file in a subdirectory.
The exports field also contains backward compatible entries to allow for continued
deep imports into the package. These compatibility entries will, however, be removed
in a future major version. Deep imported files are not considered part of the public
API of the package.
@clydin clydin force-pushed the build/core-remove-legacy-secondary branch from 9fa10ad to f5cb7dd Compare May 23, 2023 10:58
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels May 23, 2023
@clydin clydin merged commit e037dc9 into angular:main May 23, 2023
@clydin clydin deleted the build/core-remove-legacy-secondary branch May 23, 2023 14:36
@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants